Skip to content

trunk shadow changes: com.unity.mobile.android-logcat - #215

Open
pets-svc[bot] wants to merge 1 commit into
masterfrom
shadow-package/com.unity.mobile.android-logcat
Open

trunk shadow changes: com.unity.mobile.android-logcat#215
pets-svc[bot] wants to merge 1 commit into
masterfrom
shadow-package/com.unity.mobile.android-logcat

Conversation

@pets-svc

@pets-svc pets-svc Bot commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

This PR contains changes made to the trunk copy of com.unity.mobile.android-logcat.

This usually means that breaking changes has landed in the trunk Editor, necessitating matching changes to your package code. trunk is therefore currently running CI tests with the modified shadow package instead of your real package. You must integrate these changes into your package (while maintaining compatibility with older versions of Unity supported by your package), release a new version, and land the new version in the editor manifest before the Package RC deadline, as your package otherwise will not be compatible with the released Editor.

Is this automation useful? Let us know on #devs-pets, where you can also ask any question you might have about shadow packages or this automation.

Note: The shadow-package/com.unity.mobile.android-logcat branch may be force-pushed by automation at any time. If you want to make changes before landing this PR, create your own branch (and PR) to avoid automation overwriting your changes:

git fetch origin shadow-package/com.unity.mobile.android-logcat:mybranch
git checkout mybranch

If further changes are made to the shadow package on trunk, this PR will be updated if still open, or else a new PR will be opened.

@u-pr u-pr Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Harness Review

Needs changes

The updated strict assembly-reference expectation is not version-aware despite the package continuing to validate against older Unity Editors.

Reviewed commit c6678e6

🤖 Helpful? 👍/👎

"System",
"System.Xml.Linq",
"UnityEngine.IMGUIModule",
"UnityEngine.UICommonModule",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1

expectedReferences is an exact list: the loop below requires every entry to occur once. These new compiler-generated dependencies are unconditionally required even though the package is validated on 2021.3 and 2022.3 as well as current 6000/trunk Editors. In the older editor builds where these references are not emitted (the previous list did not contain either), this makes ValidateAssemblyReferences fail with a zero reference count, blocking the existing compatibility CI. Add the dependencies only for the Editor versions that emit them (using the relevant Unity version defines), rather than adding them to the common list.

🤖 Helpful? 👍/👎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants